[Cloudflare for SaaS, SSL] Clarify hostname readiness#30557
Merged
Conversation
github-actions
Bot
added
product:ssl
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
1 task
Contributor
|
This PR requires additional review attention because it affects the following areas: PartialsThis PR updates partial files, which are pieces of content used across multiple files in our Render component.
|
dinasaur404
approved these changes
May 4, 2026
dcpena
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the Cloudflare for SaaS API docs and SSL certificate status reference to clarify how to interpret the Custom Hostname Details response. The PR explains that the top-level
statustracks hostname activation, nestedssl.statustracks certificate issuance and deployment, and production HTTPS readiness requires both values to beactivewith customer DNS pointed to the SaaS target.Also notes that a successful TLS handshake alone is not the readiness source of truth because Cloudflare may present another matching certificate, and that non-wildcard custom hostnames can complete automatic HTTP certificate validation even when TXT validation was selected.
Documentation checklist